Thanks for the PR!

We’re going to close this for now.

Reasoning:

• Join/LeftJoin/RightJoin in gen are low-level helpers that accept explicit ON conditions. Users can already include soft-delete constraints explicitly when needed (e.g. add joinedTable.DeletedAt.IsNull() / field.NewField(joinedTable.TableName(), "deleted_at").IsNull() as an extra join condition).
• For relationship-based joins, DO.Joins(relationField) delegates to GORM’s Joins(...), which already applies model query clauses (including soft-delete) for the joined schema.
• The implementation here tries to infer relationships from d.db.Statement.Schema.Relationships and then rebuild SQL by string-replacing bind variables. That’s quite fragile (aliases, multiple joins, different dialectors/bindvars, statement state) and there are no CI checks/tests on the branch.

If we revisit this in the future, it would likely need a more robust approach plus coverage tests.

Closing: soft-delete can be handled via explicit join conditions or relationship Joins(); current approach is too fragile.